avoid backend_quota edit war for AZSeparatedResourceTopology #635
+26
−26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm seeing a lot of this in the DB right now:
Scrape wrote a zero into
project_resources.backend_quota
which caused quota-sync to run and write a null again. This would cause neverending unnecessary quota syncs on all project services with AZSeparatedResourceTopology resources.The second commit fixes the tests by removing a few other places that tried to set
project_resources.{quota,backend_quota}
to non-null values.